I have a doubt, there is a way to determine which attributes, when altered, that should lead to a suspect link? |
Re: Suspect links for future users that get the same doubt... Understanding suspect links In a large database with multiple links, a change to one object may affect many other objects in the database. DOORS prevents such changes being overlooked by marking objects that are linked to objects that have changed as having a suspect link. Users can check modules for suspect links, identify the change that has caused the link to become suspect, and update the objects accordingly. Note The object that is changed is not marked as having a suspect link, but any objects that are linked to that object are marked as having a suspect link. For example, if a user requirement is linked to a system requirement a change to the user requirement may require a change to the linked system requirement. The system requirement is marked as having a suspect link. but the user requirement does not have a suspect link. When the system requirement has been checked and updated as required, the suspect link can be cleared from the system requirement. If changes are made to both the source object and target object of a link, then the link will be marked as suspect at both ends. If you clear the suspect link at the source it also clears the suspect link at the target. Caution Only those attributes that have been set to affect change dates cause a link to be marked as suspect when they are edited. The Affect change dates setting can be selected by editing the attribute definition. Note In version 8 of DOORS, date values are stored on the server in UTC (Universal Coordinated Time), and are displayed on the client according to the client time zone. In pre-8.0 versions of DOORS, date attribute values did not include the information to make time zone adjustments, so date attribute values in migrated data may not display as expected. For example, if clients in multiple time zones were working on data, suspect links may not operate as you would expect. For more information about UTC, see Understanding how date and time are recorded. Thanks everyone! |
Re: Suspect links Basically, the link itself remembers the date it was last "cleared". If the Object has changed after that date then it displays all that object's attr-values that have changed after that date, and the link becomes "suspicious". IIRC the link be suspicious in either or both directions; so the SubSystem can see suspicious System changes, and the System can see the SubSystem suspicious changes. However, since the source object of the link "owns" it, it must be editable to clear the System suspicion, or something like that. -Louie |